home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
kermit.columbia.edu
/
kermit.columbia.edu.tar
/
kermit.columbia.edu
/
newsgroups
/
misc.19950726-19950929
/
000053_news@columbia.edu_Sun Aug 1 01:43:08 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1995-12-25
|
2KB
Received: from apakabar.cc.columbia.edu by watsun.cc.columbia.edu with SMTP id AA03815
(5.65c+CU/IDA-1.4.4/HLK for <kermit.misc@watsun.cc.columbia.edu>); Mon, 31 Jul 1995 22:59:32 -0400
Received: by apakabar.cc.columbia.edu id AA08444
(5.65c+CU/IDA-1.4.4/HLK for kermit.misc@watsun); Mon, 31 Jul 1995 22:59:31 -0400
Path: news.columbia.edu!panix!not-for-mail
From: mgflax@panix.com (Marshall G. Flax)
Newsgroups: comp.protocols.kermit.misc
Subject: Re: One-Way File Transfer Protocol?
Date: 31 Jul 1995 21:43:08 -0400
Organization: Currently, _extremely_ disorganized
Lines: 17
Message-Id: <3vk0rc$eq2@panix.com>
References: <3vjs4e$nip@elaine30.Stanford.EDU>
Nntp-Posting-Host: panix.com
Apparently-To: kermit.misc@watsun.cc.columbia.edu
In article <3vjs4e$nip@elaine30.Stanford.EDU>,
Dylan Mackay <opel@leland.Stanford.EDU> wrote:
>I am looking for information on one-way file transfer protocols. What
>I mean by this is a protocol that will support file transmissions in
>which the receiving side has no transmission capability at all. It
>cannot send flow control, error-checcking responses, or anything else
>it might do in traditional ftp-style protocols. Ideally, some type of
>error-checking information could be send with the file, so that the
>receiving end could interpret what it has received, and establish
>whether the transmission was corrupted or not.
I believe you are trying to describe error-correcting codes rather than
communication protocols.
marshall
--
[Marshall G. Flax -- mgflax@panix.com]